home *** CD-ROM | disk | FTP | other *** search
- Harken, hackers!
-
-
- We all know what a pain it is to keep
-
- track of a series of revisions of a
-
- single program. Here's a tip that
-
- will automate the process:
-
-
- Always make line 0 of your program
-
- a REM statement containing the
-
- statement required to save the
-
- program.
-
- Like this:
-
- 0 REM SAVE"0:HARKEN V1",8
-
- Then when it's time to save a new
-
- version, change the version number in
-
- the REM, DEL the '0 REM' part and
-
- press return.
-
- The advantages: Your program always
-
- matches its name in the directory.
-
- You never have to load a directory to
-
- see what version you should save the
-
- program as THIS time. Your programs
-
- will be numbered in sequence, without
-
- gaps.
-
- And if you forget to change the REM
-
- the only ill effect will be a FILE
-
- EXISTS error. Don't use the
-
- SAVE"@0:HARKEN V4",8 syntax, because
-
- SAVE AND REPLACE would eliminate any
-
- advantage gained by this technique.
-
-
- We at LOADSTAR have learned from
-
- bitter experience that you should
-
- ALWAYS keep EVERY version of a program
-
- (carefully numbered so you can tell
-
- them apart) until you finish your
-
- development work. You never know when
-
- an I/O error will come along and
-
- swallow your last three revisions
-
- of PACLIFTER. And you never know when
-
- you will find out you are on the
-
- wrong track. You may decide that all
-
- of your work since the sixth revision
-
- was wasted. If you can't find your
-
- sixth revision, ALL your work was
-
- wasted.
-